Hello, Welcome back to Vulcanus. It's been a while. You place your new prototype big mining drills, the pinnacle of resource extraction technology, on the closest tungsten deposit to your fledging Vulcanus factory. A few power poles later and they are happily mining away providing a new consistent source of valuable tungsten. A rail ramp and station just about fit in the area too, but without any rail supports in your inventory that line isn't going anywhere soon. Transport belt will have to do for now. As you're returning to the main factory, placing transport belt to connect this new resource to your base, you feel a trembling from the ground. Big mining drills make a lot of vibrations, but this is on a whole other level. Something else must be going on. You head back towards the mining site. Across a river of lava you see a truly gargantuan creature snake its way around a volcano. This formidable beast most closely resembles a centipede or millipede but is larger than a train. As it moves forwards the ground at its face is broken apart leaving a trail of torn up rock and patchy lava. Trees, rocks, even cliffs are torn apart by its passage. Ash is flung into the air making an abrasive cloud that blankets its body and lingers long after it has moved on. The creature roars and speeds up. As it does so it starts shaking the ground harder. Rhythmic vibrations agitate a wide area around it kicking up a huge cloud of ash and destabilising the terrain. Also available on YouTube in 4k. The creature cruises over the lava river and demolishes your machines without even slowing. Your precious new mining drills that seemed so large and powerful just moments ago look like puny toys in the face of such an unfathomable beast. The Demolisher continues its path of destruction down the line of transport belt toward your base, but before getting there it slows to a crawl and turns back into the volcanic wastelands. This attack won't go unanswered. It's time for a fight. You pursue the Demolisher, an easy task given its thick glowing trail. Lava on either side of you forces you to cross through the trail to pursue the creature. The torn up terrain is hot, but there are enough cool rock sections to step across it. As you do, the lingering ash cloud around it obscures your vision and the abrasive particles interfere with your exoskeleton equipment. You catch sight of the body again, this time up close. The thickly armoured plates of each segment seem to give it good protection from heat, and probably many of your weapons. It hasn't reacted to you yet, perhaps it has not seen you, or perhaps it does not care. You move towards the Demolishers head and it still ignores you. The face appears to be a clear weak spot. It has no eyes and the skin still seems adapted for the heat, but the armour is much thinner around the jaws. Bracing yourself for a reaction, you shine your lasers at it's face, but nothing. It continues to patrol some path, as though you were nothing but a speck of dust on the wind. A rocket to the face would surely provoke it, but before testing that theory, you place a line of land mines to secure your retreat. There's an immediate reaction from the creature. It speeds up and turns towards you. Once again, rhythmic vibrations shake the terrain and generate a steadily expanding cloud of ash. The cloud quickly encompasses you. Obscured vision and snagged exoskeleton joints will limit your speed. You fire your submachine gun at the creature. Your piercing rounds cut into the Demolisher and do some damage, but by the time you reload a new magazine all the damage you dealt has healed back. You try again for a few moments inflicting some damage, but again, it seems to heal faster than you can deal damage. Vibrations coming from the creature seem to focus and amplify around you destabilising the ground even more. The crust is thin at the best of times and this isn't helping. A fissure starts to open up under your feet. You manage to dodge to the side as a volcanic eruption explodes in the area you stood a moment ago. Rock fragments, lava, and hot gases shred the area. You avoided the main blast, but just being close to the edge was enough to weaken your shields. New fissures start to open up around you. These are easier to dodge now that you know to look for the fissure signs in the ground. Standing far enough from the eruption is completely safe but you'll need to stay on your toes. The Demolisher ploughs through the line of land mines and does not slow as it does so. They do more significant damage, but to your horror the damage is gone in seconds. That was your escape plan, it's time to get moving. You try some more weapons as you move away, even throwing a few spare defender capsules into the mix. They're all somewhat effective but the damage doesn't stick. You'll need to deal damage much faster but you weren't prepared for that. While distracted you fail to dodge a new volcanic eruption. The fissure erupts directly beneath, shattering your shield and blanketing you in fire. The power armor stops you from getting too singed but another hit like that would be certain death. For now, this is not a fight you can win. You switch all your focus to dodging the eruptions and moving away. A few seconds after you stop firing the Demolisher slows down and turns back. That's two wins for the Demolisher, but you'll live another day.

Hello, here is another update on progress in delivering perks from the alpha preorder. The game development itself is going along quite well. The updates are coming out more or less once a month. This gives the people who have bought the alpha access a sneak peek at the Factorio evolution in progress. Some time ago we have also introduced the first version of the scenario pack. The forum community helped us to tweak the bugs and balance the missions. The result are three mini campaigns that provide various factory-building challenges to the player: Tight spot - Little space, limited resources and fixed amount of time. Buy land and machines and sell your final product. Transport Belt Maddness - So many chests and such a small island. Can you connect the chests without your head spinning? Supply challenge - Six hungry chests that change their taste often. Is your production flexible enough? These missions are the first batch and there will be more coming in the future. The scenario pack is available to the Furnace Attendant tier or higher. Another update in the same tier is a new Factorio wallpaper displaying the Assembling machine in the night. The Mining Drill Operator tier has been updated as well. For a while there has been an option to put your name in the game. Quite a few people already did this and now there are train stations named after them in Factorio. As of 0.6.0 the name generator will be used for Labs as well. Another update for this tier is the first version of the Concept Art book that is available for download now. As mentioned before this is some very early Factorio concept art and the book will definitely be updated as the game development progresses. Last update regards the access to our internal art wiki. The Mining Drill Operator members (or higher) from now on can observe the evolution of the in-game graphics via a read-only access to the wiki. There are plenty of sketches, inspirational photos and different variants of the game objects. The wiki is hosted on the google pages, therefore the google login is necessary. For now the invitations will be send on request. That means if you are a Mining Drill Operator member (or higher) then send us an email with your login name and we will send you an invite. This process will be automated in the future:D Here comes just a tiny recent preview of things you can see there: the evolution of new electric furnace model.

Hello!

Hello, you can sit tight, because the batch of insiders from the world of Factorio development are here.

Good afternoon everyone, We have commited to releasing the 0.11.0 on 31st of October 2014. That is next Friday. If all goes well, this will be our Halloween present to the community. But there is a busy week ahead of us:) Apart from regular pre-release craziness, doing significant refactorings the day before or fixing bugs at the last minute, there will be more. On Wednesday we have scheduled moving to our new office and on Friday morning (yes that is the release day) we will be giving a presentation at a local university about the project. We gave the same presentation about a year ago when it was not exactly clear whether / how long will we be able to continue working on Factorio. That has definitely changed for better, especially considering we are moving out of "our garage" (our apartment used as a working place), looking for people to work with us and doing other sorts of longer term commitments.

Hello, this week's Friday Facts is brought to you by Michal (one of the new guys). We are getting close to release of 0.12. We're trying to fix as many bugs as we can; trying to get everything stable and polished. Currently we are so busy that we even haven't had time for any team building activity with Rseding91 who has come to visit us for next few weeks. So, I am going to take advantage of this no-big-news week to present more closely a feature I have been working on for the last month or so.

Hi there, fifth anniversary for the Friday Facts is here. Nothing big, but we got into the mood of doing these updates regularly and so far it works fine. The release clock has stopped on 0.7.4. This looks pretty stable though there were still some minor annoyances and rare crashes. So the show goes on and there will be a 0.7.5. That will make the 0.7 a release with most bugfix subreleases so far. Actually Kovarex took it as sort of a challenge to fix all the bugs that are reported on our forum (which works as a kind of bug tracker for us). Now there are last four. Actually this led us to a rather interesting conversation about the bugs and our approach towards them. We have always took the stance of fixing bugs first, adding features later. This is contrary to some very popular and successful indie games out there. So we naturally wondered whether it makes sense for us to keep doing this or whether we should try to move forward faster and build more features (there is plenty on the list). The conclusion was that it is important to find a balance. Crashes and bugs which prevent someone from playing or are annoying are not tolerable and must be fixed immediately. However we will be spending less time on tiny little bugs. Things like "if you are in the god mode and select a gun turret and pause the game and open the menu, then the description of the gun turret is broken". Obviously a made up example to demonstrate the point:). We are really grateful that people are reporting even the smallest bugs, it's just that we think we need to draw a line and don't be afraid to say "this is tolerable now and we will fix it later". This will allow us to spend more time with the new features and content. Which is what we really need at the moment. On the side note the work on the trailer is in the full speed. As mentioned before we have decided to go for a not so traditional approach without scene cuts. So the trailer will basically present an existing factory by sliding the camera from one place to another. The factory is done. Actually I took the factory from one of my freeplay games and adjusted it to fit the trailer's needs. Now we work on the script logic behind it. The script controls everything. Movement around the factory, speed, zoom, dynamic adjustments to particular machines, timing of actions, etc. This is also positive because it led us to extending the Lua API - for instance we have added routines to control the trains. These changes will be available in the 0.8 together with the trailer map and the script. There is still a lot of work ahead - finishing the script, balancing the speed and flow, polishing. After all this is done we will just press a button and capture the trailer from the screen. Lastly we will need a background music and sound. We haven't arranged anything yet, but Albert has some good contacts among sound professionals who could do this for us. There probably will be some spoiler discussions regarding the trailer on our forums soon. For the impatient there is a screen shot of a possible first trailer scene below (still needs some polishing - namely new terrain and additional decorative objects). There is a link on our forum to this blog post so feel free to share your comments. To finish with the fun fact there is now over 7000 commits in the Factorio project repository. And counting.

Hello, The title says it clearly. After a long long time, one of the most core elements in the game has been graphically redesigned to fit the art direction. Albert played around with couple of shapes and in the end the winner is surprisingly lightweight and elegant. If you are impatient to see how the new inserters look like, then scroll down and check them out on the screenshot from one of our playtesting games. This is one of our many final preparations for the new trailer, which has been supposed to be finished so long time ago it is not even funny. Today we have released the 0.9.2. Regular bugfix release at regular time with regular expectations (meaning that more bugs are expected to be found - the forum users are becoming pros in this :)). There are also couple of small balancing changes that should make the game slightly better (namely that poison capsules will hurt worms as well now, oil industry is not needed for making cars and trains and that pipe to ground is longer). Check out the details for yourself. While this release still will probably not become the stable release, we feel we are slowly getting there. We are about to start planning what to do after 0.9 is stable. As mentioned couple of times in the past we feel that the time has come to take on the multiplayer. This will be a gargantuan task indeed - at least for us, maybe Chuck Norris would wrap up the whole thing by simply giving the 0s and 1s on the hard drive an angry look. But he has better things to do I guess, so it is up to us to do it the old fashioned way - designing and writing the code. So the MP will be developed in a separate branch by +- 2 people (we will be rotating), this will leave some small development power to carry on with the standard release cycle - working on little features and improvements, integrating new graphics, etc. And just to clear up the speculations, the next planned release will be 0.10 not 1.0 :D Now a small rant on Indie vs. AAA. Recently kovarex has played quite a bit of Starcraft II - namely the Terran and Zerg campaigns. I was watching him playing now and then. He was extremely positive about the whole experience. Namely the level of detail and playability were supposedly superb. Playing AAA games can be quite intimidating for the Indie developer. But then there are the credits. It turned out that SC II was done by a LOT of people. We don't have the exact numbers but we suppose there will be like couple of hundreds of people in the team. We have 4 people in the core team now (plus we work with freelancers here and there). So we made some rough estimates taking into account that SC II took 7 years to develop and it sold around 5M copies. Let's presume it will take us at least till next years summer to "finish" the game (see the last post:)). Let's also assume that we will manage to sell 50k copies by then (which we believe is doable). After some rounding (yeah many things can be achieved by "good rounding") and some math we get that we could have 0.5% of costs and also 0.5% of revenue compared to SC II. So in the end the Indie vs. AAA struggle doesn't look that futile :) We are always eager to learn what you think at our forums.

Hello, this week the Friday Facts are coming a little bit earlier. The reason is that in the evening I will be lost somewhere in the middle of Brno (second biggest city in the Czech Republic). I will participate in a popular annual deciphering game that is taking a place there. The 0.7.5 with another batch of bugfixes went out this Tuesday. Since then there has been no reports regarding major issues or crashes. Couple of teeny-tiny bugs were reported however that is not enough for us to make a new release now. So the 0.7.5 will become a stable version. Finally:) I have spent most of the time during the past week working on the trailer. The first version has been done already. There is a discussion thread on our forum (with a link to the unlisted video on youtube) where people can give us feedback about it. This is by far not finished. But we needed to get it out in order to start talking to the music & sound guy and give him some baseline to work with. Yesterday we had a long chat with Albert about the trailer and we agreed that the first scene (standing in the middle of the ruins) should be changed. Now it feels too out of the context from the rest. Apart from that we are quite happy with the general flow. Of course there are plenty of details that need to be tweaked so there is still a long way to go. On the other hand having all the trailer in the script makes things a hell lot easier for us. Changing things like the zoom behavior, camera movement or speed is just a breeze. Same goes for extending / shortening the scenes or adding a new scene all together. Another issue is the final video quality. There is a lot of movement going on in the trailer and currently after youtube compression, often the video is just blurry. We have used the 720p for now but that proved not to be enough. Oh and regarding the music. Just for fun we tried to run the Raymond Scott's Twilight in Turkey together with the trailer. It turned out to work surprisingly well, so one option is that the music would go in this kind of direction. Apart from preparing the 0.7.5 Michal spent most of the time on the new scenarios for the main campaign. It starts to slowly shape. At the moment there are 5 levels that introduce basic things like assembling machines, research, trains, etc. to the player in the course of playing. Often the player is not starting from the scratch but he can use already existing pieces of the factory. Writing the scenarios (and the trailer) is also a good opportunity for us to review, document and extend the Lua API. Kuba and Albert keep working together on the terrain. There are couple of variations of the dirt by now and Albert is now spending his evenings with the grassy terrain. Kuba made couple of Blender scripts to ease the manual terrain work. This way Albert can take advantage of generated tileable noise or terrain transitions. Also yesterday Kuba showed me a great picture he generated that I can't resist to share with you. In case that you always thought that there is a lot of recipes in the game and that the whole thing is too complex, then worry no more. Here is an ultimate Factorio recipe cheatsheet for you: As usual there is a post on our forum where you can discuss this update.

Hello, after a long long time the 0.9.8 was marked stable this week. There were no big ovations or cheering, just a quite "stable sticker exchange":) The bugs forum is not empty though, as someone would expect. Quite a few small issues remain, but for the sake of moving on we decided to put them to our backlog and mark the release as stable. However if some game crashing or very serious bugs are discovered in 0.9.8, we will make a hotfix. Oh, and the good thing is that we managed to break the streak (for now) of ever increasing number of bugfix releases (the 0.9 had 8 bugfix releases - the same as 0.8). The whole "programming department" has been fully commited to the work on multiplayer for a while now. The task divison for now is following: Michal - fully deterministic simulation. This is an absolute must, because all multiplayer peers will calculate the simulation themselves and only the player input (we call it input actions) will be exchanged over the network. Nice effect of having deterministic simulation will be having functional replays again (hmmm not really again because there have always been some bugs in them even when they were "working":)). Kuba - lower level network layer. This includes the connection management, packets management (we will be using UDP for all the communication) and eventually things like NAT punching to allow connections for peers behind NAT (few people have public IP address). Tomas - synchronization layer. This logic will take care of keeping the simulation state same for all the players in the game. This includes queing up the input actions, sending them out in batches (tick closures to other peers), requesting missing tick closures, etc. These things are absolute minimum necessary for our multiplayer implementation. However there is more to be done after this, things like: starting the game (the lobby), mechanism for a player joining already existing game, hiding the latency for the player (most of the time the actions for different players will not collide so we can act as if common actions - like moving the player around - were confirmed immediately) and more (see our battleplan whiteboard in one of the previous friday facts). There is a lot of work ahead, but the good news is that we have finally fully dived into it. We will keep you updated about the progress:) Albert has finished with most of the map trailer tweaks. Today we also did a first test with exporting the trailer using the new screenshot mechanism. We did this on Michal's computer which is way more powerful than mine (it does take a while to export 3600 screenshots). However there was this funky bug that parts of the terrain in the screenshots had strange, kind of inverted, colors. We have spent like half a day looking into this issue. Finally it turned out to be a problem in our custom optimized version of d3d drawing routine (this was happening on windows only). Spending hours in frustration hunting bugs (that are not even visible to the player in the end) happens more often than you would think, so game programming is not just about sitting back, playing video games and calling it "research" (but that is part of the job too:)) Anyway to give you an idea of what was going on you can see a visualization of the problem below. For better effect (and for us to easier analyze the problem) the corrupted regions of the image (here all of the terrain) are drawn with reddish overlay. Any idea for the picture title? Want to cheer us up for the multiplayer work? Or feel like laughing at us for taking so long with the trailer? Go to our forums.